home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++
- Subject: Re: C/C++ knocks the crap out of Ada
- Date: 7 Mar 1996 09:05:29 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4hn50pINN4r8@keats.ugrad.cs.ubc.ca>
- References: <00001a73+00002504@msn.com> <4h7jskINNnph@anvil.ugrad.cs.ubc.ca> <dewar.826146475@schonberg> <4hmlca$a30@solutions.solon.com>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <4hmlca$a30@solutions.solon.com>,
- Peter Seebach <seebs@solutions.solon.com> wrote:
- >In article <dewar.826146475@schonberg>, Robert Dewar <dewar@cs.nyu.edu> wrote:
- >>I guess that means "rarely used in the academic programs that I am fiddling
- >>with". In real life of course, they are a vital, and widely used part of the
- >>language.
- >
- >I have to admit, I've only seen them used in NetHack. No other code I've
- >ever read used bitfields. :)
-
- >They'd probably show up a lot more with industrial or embedded systems.
-
- I have seen them used in a very implementation specific way as a method to
- access various status bits of a certain device on a Sun 3 machine, using the
- bitfield structure as a syntactically convenient lvalue to ``go through''.
-
- The only thing that bitfields are good for, portably, is optimizing the
- storage of small signed or unsigned integers or flag sets, at some
- computational expense.
- --
-
-